From 7bbdb62a8a372f7fa5031f82bcd36bbb052c2251 Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Tue, 4 Aug 2026 17:16:26 +0000 Subject: [PATCH] Load (some) SIGHTING_RECORDS during conversion --- conversion/load_support.sql | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/conversion/load_support.sql b/conversion/load_support.sql index ab9fd7e..3063666 100644 --- a/conversion/load_support.sql +++ b/conversion/load_support.sql @@ -142,6 +142,14 @@ INSERT INTO role_codes (role, description) , ('Solo', 'A participant in an event, non-directed when there are mulitple participants'); +-- Add the special values to SIGHTING_RECORDS, because it makes testing +-- eaiser +INSERT INTO sighting_records (code, priority, description) + VALUES ('MANUAL', 0, 'A manual adjustment') + , ('MATINGS', 1, 'Sighted mating') + , ('ARRIVALS', 2, 'Recorded arriving during a follow') + , ('ARRIVALS_A', 3, 'Sighted arriving at the feeding station'); + -- It'd be nice to analyze the whole db, but Azure gives us errors. -- Instead, be explicit and analyze the tables loaded. ANALYZE arrival_sources -- 2.34.1